Add trigger_error as Log Destination Option#1939
Add trigger_error as Log Destination Option#1939SoulofAkuma wants to merge 2 commits intoopen-telemetry:mainfrom
Conversation
|
I'm gonna have to double check whether I classify as an individual or corporate contributor in this scenario. I am participating in the bloomberg open source series with OTel. |
|
Submitted corressponding documentation update: open-telemetry/opentelemetry.io#9685 |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1939 +/- ##
============================================
- Coverage 68.10% 68.09% -0.01%
- Complexity 3021 3023 +2
============================================
Files 450 451 +1
Lines 8820 8824 +4
============================================
+ Hits 6007 6009 +2
- Misses 2813 2815 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 4 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Co-authored-by: Chris Lightfoot-Wild <github-clw@wild.me.uk>
2 participants
This PR adds
trigger_erroras an additional option forOTEL_PHP_LOG_DESTINATION.I will add a corresponding PR to https://github.com/open-telemetry/opentelemetry.io to document this new option and will reference this PR here as soon as that is done.
Fixes #1473